>>The string class stuff currently in the MiscKit looks nice,
>>but I think I'd like to see it broken up into a small heirarchy
>>of classes.
> Another possibility is splitting up the .m file into components
> to make them more manageable, but again it means more files.
> I'm not sure if it's possible to decide which sections get included
> or not.... if so, that is another possiblity - allow the programmer
> to decide which sections of code they want want to bring in.
Isn't this precisely what "Categories" are for? The essential functionality is in the class; creeping features go into the categories. Normally, the '.m' files get compiled into a library, and the user includes '.h' files for whichever methods he wants to call. For a developer wanting to use the kit in this application, he can start with the class, and then add whichever categories (both .h and .m files) he needs.
- Ernie P.
---
Ernest N. Prabhakar Caltech High Energy Physics
Member, League for Programming Freedom (league@prep.ai.mit.edu)
CaJUN President NeXTMail:ernest@pundit.cithep.caltech.edu
"...and ourselves, your servants for Jesus sake." - II Cor 4:5b